Calls of blocks: functions or function blocks

Use →calls in the →graphical editor →FBD to call a →function or a →function block. A catchall term for functions and function blocks is "→block". If you read about blocks in the Neuron Power Engineer user documentation, the description is about functions and function blocks (unless otherwise clearly stated).

A call may get values from other elements via its inputs, the value of the call may be assigned to other elements via its outputs. →Assignments are visualized by lines connecting a call with the other elements.

It is not possible to insert calls of the following language elements in the FBD-editor:

  • →interfaces

  • →methods

  • derived function blocks (= function blocks using the keyword EXTENDS)

  • abstract function blocks (= function blocks using the keyword ABSTRACT)

Representation

Usually, the input connection point (short: input) of the call is located on the left side and the output connection point (short: output) on the right side. The layout of the call (e.g. the color) is determined by a default layout.
(info) Use the interface editor, if you want to change the predefined layout attributes for user-defined blocks (e.g. the orientation of the in-/outputs).

Peculiarities

  • More in-/outputs might become visible for an extensible block, if the call is enlarged and the setting Expandable within the interface editor is checked. Example: The AND block is displayed with 2 inputs at least. When it is enlarged, up to 16 inputs are displayed. 
    A certain number of the inputs of an extensible block must be connected (usually it is 2 inputs). Observe that input variables of extensible system functions that are not connected get the default →initial value.

  • If you connect the input/output of a block for safe logic to a safe data type, the background color of this block might be changed to a shade of yellow. Details: See "Highlighting safe logic in the FBD-editor".

  • →In-/out variables within the interface are indicated by the straight line between the input connection point and the output connection point.
    Example for calling the user-defined block MyFB (incl. assignments by a value field) that contains an in-/out variable named In_Out1:

    However, if a block with in-out variables has been migrated from logi.CAD/32 to Neuron Power Engineer, the following is valid: Neuron Power Engineer displays the user interface of the block as it is in logi.CAD/32. This means that only the input connection point of the in-out variable is displayed in Neuron Power Engineer. It is also possible that other variables are located on the opposite position of the input connection point.

  • value field with the interface for a block is displayed as long as the respective input is not connected with an FBD-element.

    Example for the block interface in which the value of the input is assigned to its opposite output (the value is predefined by the 2 value fields within the interface):

 

(info) Depending on the configuration of your Neuron Power Engineer version, the FBD-editor and its elements might be displayed differently in your Neuron Power Engineer version than illustrated in the IDE documentation. This is the case, if Neuron  or the system integrator has activated the smart styling or one of them has changed the styles for the FBD-editor. Subsequently, the illustration in the IDE documentation are symbolic images and the representation in your Neuron Power Engineer version takes precedence for the valid representation. In case of doubts, please contact Neuron or your system integrator.

Neuron recommends that you and/or your system integrator do not use yellow shades when designing FBD-elements because the color "Yellow" is used for tracking safe signals when developing safety-related applications. This recommendation applies in particular when you are using the legacy styling. Neuron Power Engineer does not check if colors are already used elsewhere. So the use of the yellow shades by you and/or your system integrator could have the consequence that "yellow" might also identify a non-safe logic as well.

Actions for calls